Microsoft docx export issue.
So I ran into a slight issue while testing the .docx export features of FastReport.
If you want to follow along, go ahead and save one of your reports as docx.
The document will save in the Word 2007 XML format. Open the new document and you should get a missing proofing tools message on the document (if you've never click the 'Never Show Again' box).
I saved the docx file as a zip file to check out the styles.xml file and found a language default setting for 'minorEastAsia'. You can remove the docDefault block for this the message goes away.
I've attached two images. The first is of the missing proofing tools message and the second is an example of the styles.xml file to show what the rPrDefault looks like.
Now I know the export works and I shouldn't be complaining, but our customers will point out and complain over every idiosyncrasy they can find. I was wondering if any of you have found a way to get rid of this block programmatically or know of a workaround.
If you want to follow along, go ahead and save one of your reports as docx.
The document will save in the Word 2007 XML format. Open the new document and you should get a missing proofing tools message on the document (if you've never click the 'Never Show Again' box).
I saved the docx file as a zip file to check out the styles.xml file and found a language default setting for 'minorEastAsia'. You can remove the docDefault block for this the message goes away.
I've attached two images. The first is of the missing proofing tools message and the second is an example of the styles.xml file to show what the rPrDefault looks like.
Now I know the export works and I shouldn't be complaining, but our customers will point out and complain over every idiosyncrasy they can find. I was wondering if any of you have found a way to get rid of this block programmatically or know of a workaround.
Comments
I just ran into the same problem. Is there a fix?
@Polomint is right, is better create a Ticket, This morning FR solve the errors with TFrxDocXExport component
@Polomint you're right I never added a ticket, I figured omitting the code in the export would fix it for me. I'll have to check out the most recent update too see if I'm good to go.